🌐 Web query:

dbt dateadd macro documentation

💡 Result:

dateadd is now documented as a dbt Core cross-database macro (namespace: dbt), not in dbt_utils (those cross-db macros were removed from dbt_utils starting in v1.0). [1] (docs.getdbt.com)

dbt dateadd macro (Core)

Signature

{{ dbt.dateadd(datepart="day", interval=1, from_date_or_timestamp="..." ) }}

Args

• datepart: a date/time part (database-specific)
• interval: integer (positive or negative)
• from_date_or_timestamp: a date/time expression [1] (docs.getdbt.com)

Examples

{{ dbt.dateadd(datepart="day", interval=1, from_date_or_timestamp="'2016-03-09'") }}
{{ dbt.dateadd(datepart="month", interval=-2, from_date_or_timestamp="'2016-03-09'") }}
``` [1] ([docs.getdbt.com](https://docs.getdbt.com/reference/dbt-jinja-functions/cross-database-macros))

### Sources
- [1] dbt Developer Hub — “Cross-database macros” (includes `dateadd`) ([docs.getdbt.com](https://docs.getdbt.com/reference/dbt-jinja-functions/cross-database-macros))  
- [2] dbt-utils README note about cross-database macros moving to dbt Core ([github.com](https://github.com/dbt-labs/dbt-utils?utm_source=openai))

Citations:

- 1: https://docs.getdbt.com/reference/dbt-jinja-functions/cross-database-macros
- 2: https://docs.getdbt.com/reference/dbt-jinja-functions/cross-database-macros
- 3: https://docs.getdbt.com/reference/dbt-jinja-functions/cross-database-macros
- 4: https://docs.getdbt.com/reference/dbt-jinja-functions/cross-database-macros
- 5: https://github.com/dbt-labs/dbt-utils?utm_source=openai

---

🌐 Web query:

`DATEADD function Snowflake Redshift PostgreSQL BigQuery compatibility`

💡 Result:

### `DATEADD` compatibility overview (Snowflake vs Redshift vs PostgreSQL vs BigQuery)

| Engine | Has `DATEADD`? | Add *N* units to a date/time |
|---|---:|---|
| **Snowflake** | Yes | `DATEADD(part, value, expr)` (aliases: `TIMEADD`, `TIMESTAMPADD`) [1] |
| **Amazon Redshift** | Yes | `DATEADD(datepart, interval, expr)` [2] |
| **PostgreSQL** | **No** (built-in) | Use arithmetic: `timestamp + interval '1 day'`, `date + integer` (days), etc. [5] |
| **BigQuery (GoogleSQL)** | **No** (`DATEADD` name) | Use typed functions: `DATE_ADD(date, INTERVAL n part)`, `DATETIME_ADD(...)`, `TIMESTAMP_ADD(...)`, `TIME_ADD(...)` [3][4] |

---

## Syntax mappings

### Snowflake → Redshift (nearly 1:1)
Both accept the same 3-argument pattern: `(part, number, expression)` [1][2].

```sql
-- Snowflake / Redshift
DATEADD(day, 7, some_ts)

Snowflake / Redshift → BigQuery

BigQuery uses *_ADD(expr, INTERVAL n PART) (note the INTERVAL clause and PART position) [3][4]. Google’s Snowflake migration guide summarizes this mapping as:

• DATEADD(part, value, dateOrTime) → DATE_ADD(date, INTERVAL value part) [6]

-- BigQuery
DATE_ADD(some_date, INTERVAL 7 DAY)
TIMESTAMP_ADD(some_ts, INTERVAL 7 DAY)

Snowflake / Redshift → PostgreSQL

PostgreSQL typically uses + interval (and for date, + integer adds days) [5].

-- PostgreSQL
some_ts + interval '7 day'
some_date + 7

Key behavioral gotchas (portability)

• Return type differences when input is DATE and you add sub-day units

  • Snowflake: adding hour/minute/second to a DATE returns a timestamp (TIMESTAMP_NTZ) starting at midnight [1].
  • Redshift: DATEADD returns TIMESTAMP for date inputs (date becomes timestamp at 00:00:00) [2].

• Month/quarter/year end-of-month behavior

  • BigQuery: for MONTH/QUARTER/YEAR, if the target month is shorter, the result becomes the last day of that month [3].
  • Snowflake: warns that year/quarter/month can shift the day-of-month when the result month has fewer days [1].
  • PostgreSQL interval math explicitly uses “last day of month” when needed while applying the months field of an interval [5].

• BigQuery TIMESTAMP_ADD supports only up to DAY

  • TIMESTAMP_ADD(..., INTERVAL n DAY/HOUR/MINUTE/...) is supported, but not MONTH/QUARTER/YEAR for TIMESTAMP_ADD [4]. (Use DATETIME_ADD, or convert to DATETIME/DATE where appropriate.)

Sources: Snowflake DATEADD [1], Redshift DATEADD [2], BigQuery DATE_ADD [3], BigQuery TIMESTAMP_ADD [4], PostgreSQL date/time operators & interval rules [5], BigQuery Snowflake translation guide [6].

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.